TypescriptHero only applies it's changes on save, it does not apply changes when `standardize is run via the CLI because there is no way to run TypescriptHero from the command line. These two tools can also have disagreements when it comes to single imports that exceed the maximum line length (one enforces a wrap, one allows the line to exceed). This can cause extra line changes on PRs that muddy the review process and can lead to mistakes or import issues slipping through.

import-sort performs a similar function regarding managing imports but offers a CLI option as well, so it can be run before prettier on CLI functions. This way, the VSCode changes on save sync with the CLI actions during the (updated) standardize script. Settings are kept in package.json just like prettier.

NOTE: One downside to import-sort is that it does not automatically remove unused imports, so those must be managed manually. Luckily, VSCode now highlights those, and they are not difficult to identify.

I've chosen the module sort style for typescript. It groups imports by source module, and separates imports from external libraries and imports from local files with an empty line, which is a nice distinction, in my opinion. There are alternate sort styles available.

References:
https://github.com/renke/import-sort